/doc/context/sources/general/manuals/units/units-mkiv.tex
+++ b/doc/context/sources/general/manuals/units/units-mkiv.tex
@@ -347,12 +347,10 @@ we give an example below.
\stoptabulate
The \type {_} character serves as placeholders. There are some
-assumptions to how numbers are constructe
two ways. One
>>> rather obvious failure—at least, it becomes obvious when the macro is
>>> tested—is that
>>> all the empty lines of the file are omitted. The reason is that the \par
>>> command at the
>>> end of an empty line doesn’t start up a new
new paragraph, because it occurs
> > > in vertical
> > > mode. The other failure is not as obvious, because it occurs much less
> > > often: The \tt
> > > fonts contain ligatures for Spanish punctuation, so the sequences ?‘ and
> > > !‘ will be
> &
f these defects can be cured by
> > inserting
> >
> > and
> >
> >
> > «When INITEX creates a brand new TEX, all characters have a space factor
> > code
> > of 1000, except that the uppercase letters ‘A’ through ‘Z’ have code 999.
> > (This
> >
ntain ligatures for Spanish punctuation, so the sequences ?‘ and !‘
> > will be
> > printed as ¿ and ¡ respectively. Both of these defects can be cured by
> > inserting
> >
> > and
> >
> >
> > «When INITEX creates a brand new TEX, all characters have a space
o
> you see why?) Plain TEX redefines a few of these codes using the \sfcode
> primitive,
> which is similar to \catcode (see Appendix B); for example, the instructions
> \sfcode‘)=0
> \sfcode‘.=3000
> make right parentheses “transparent” to the space factor, while tripling the
parentheses “transparent” to the space factor, while tripling the
stretcha-
bility after periods. The \frenchspacing operation resets \sfcode‘. to
1000.»
--
If at first you don't succeed, you must be a programmer.
___
If your
t; \startsetups [three]
> THERE
> \stopsetups
> \stopsetups
>
> \setups[one] \setups[three]
>
> \setups[two] \setups[three]
>
> \stoptext
>
> As part of the ongoing improvements on math rendering we added some
> classic lm/cm kerns (between u
[one] \setups[three]
\setups[two] \setups[three]
\stoptext
As part of the ongoing improvements on math rendering we added some
classic lm/cm kerns (between upperacse and periods / commas) in the
goodie files.
Some lowlevel manuals have been extended, explaining experimental 'named
cross macro
Hi list,
I'm looking to perform text replacements.
\definereplacement[SubstPostmeridian][
match={[Pp].[Mm].]},
replace={\cap{pm}}
]
The \replaceword command doesn't handle periods well. The translate module
doesn't seem flexible enough to cover edge cases. Consider the following
example
I have been using \endash, \emdash, and \figuredash in place of the various
types of dashes in my document, \quotation{} around quotes, etc. so basically
the only really punctuation appearing in the tex file are periods, commas,
semi-colons, colons, apostrophes, and question-marks. The problem
Thomas A. Schmitz via ntg-context schrieb am 23.01.2022 um 21:13:
This is a FAQ: you can't mix keywords and assignments, hence:
\startitemize [n,text] [stopper=]
Put a comment after the second argument to get rid of the extra space
before the first item.
\startitemize [text,n]
This is a FAQ: you can't mix keywords and assignments, hence:
\startitemize [n,text] [stopper=]
Thomas
On 23.01.22 21:05, Joel via ntg-context wrote:
Strangely when I use `\startitemize[text, n, stopper=]`, which I hoped
would make the period go away, I just get a regular bulleted list, it
I am trying to create an in-text list, with parenthesis, but without the period.
If I use this `\startitemize[text, n]`, I get an in-text list, but there are
periods:
There are many kinds of animals at the children's zoo: (1.) rabbits, (2.) pigs,
(3.) sheep, and (4.) dogs.
Strangely when I use
authors.
> (2) Most fields in the in-text citation are separated by commas, while the
> list citation uses periods in these places.
>
> Is there already a mechanism for handling this for another citation style?
> And if not, could anyone offer a suggestion on how I
uthors.
(2) Most fields in the in-text citation are separated by commas, while the
list citation uses periods in these places.
Is there already a mechanism for handling this for another citation style?
And if not, could anyone offer a suggestion on how I might go about
implementing separate rules f
to use only ASCII characters
for the file names and avoid anything which is special in TeX,
using spaces or extra periods should be avoided as well.
2. Arguments for \component etc.
In my example I passed the argument to \component, \startproduct
etc. in square brackets but this is only a alternative
back in the day, I would never try to use fonts
for "drawing". Especially, math fonts, where every designer has a different
idea of what the shape should look like.
ah pictex memories ... drawing lines with cmr5 periods ...
but actually, we can define a stable font with symbols in me
liographies, e.g.:
> ) plus . , ; :
> The trouble is that excessive space is often introduced between
> thebracket and the punctuation. I can control the excessive space
> thatsometimes occurs between ) and . by using )\periods[1], although
> thisruins the protrusion if it occurs
and the punctuation. I can control the excessive space that
sometimes occurs between ) and . by using )\periods[1], although this
ruins the protrusion if it occurs at the end of a line.
Does anyone know how I might be able to somehow "tie" ) to . , ; : so
that the distance remains reasonab
is that excessive space is often introduced between the
bracket and the punctuation. I can control the excessive space that
sometimes occurs between ) and . by using )\periods[1], although this
ruins the protrusion if it occurs at the end of a line.
Does anyone know how I might be able to somehow &quo
that it can
be used by the \dotfill command?
dotfill is actually a plain tex command using periods and spacing from
the math font / mode ... (maybe we should redefine it to behave
differently in text mode)
you can use this:
\definefiller
[myfill]
[symbol=.,
method=middle,
width=.5
of d’Alembert. (The authorhash does have the
hyphen for the Quérard entry.)
So, the question is, what can be done to get the desired (APA defined)
order (alphabetize letter-by-letter, ignoring spaces, capitalization,
hyphens, apostrophes, periods, and accent marks)?
Beyond that, what can be done
,
% focus=standard,
]
\starttext
\startchapter[title=Some Title, reference=pt:ref]
Lorem ipsum dolor sit amet, \periods
\startplaceformula[reference=eq:ref]
\startformula
c^2 = a^2 + b^2.
\stopformula
\stopplaceformula
Lorem ipsum dolor sit amet, \periods
\startitemize[r
mapping only when full-stop is preceded and
succeeded by a digit. This will, among other things, leave the
end-of-equation periods unchanged.
Here is how I tried to achieve it.
\startluacode
digits = { 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x
do not want to simply map 0x2E to 0x66B, because
>> then "full stop" outside a number will also change. In particular,
>> I'd like to have the mapping only when full-stop is preceded and
>> succeeded by a digit. This will, among other things, leave the
>
However, I do not want to simply map 0x2E to 0x66B, because
then "full stop" outside a number will also change. In particular,
I'd like to have the mapping only when full-stop is preceded and
succeeded by a digit. This will, among other things, leave the
end-of-equa
full-stop is preceded and succeeded by a
digit. This will, among other things, leave the end-of-equation periods
unchanged.
Here is how I tried to achieve it.
\startluacode
digits = { 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39 }
-- 0x66B instead of 0x2F gives an error!
replacements =
map 0x2E to 0x66B, because then "full
>> stop" outside a number will also change. In particular, I'd like to have
>> the mapping only when full-stop is preceded and succeeded by a digit. This
>> will, among other things, leave the end-of-equation periods unchanged.
>>
>>
. This
> will, among other things, leave the end-of-equation periods unchanged.
>
> Here is how I tried to achieve it.
>
>
> \startluacode
> digits = { 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39 }
> -- 0x66B instead of 0x2F gives an error!
> replacements = { [0x002
mong other things, leave the end-of-equation periods unchanged.
Here is how I tried to achieve it.
\startluacode
digits = { 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39 }
-- 0x66B instead of 0x2F gives an error!
replacements = { [0x002E] = { 0x2F } }
fonts.handlers.otf.addfeatur
c should be preferred.
>
> There are two layers, actually (at least in LaTeX; not sure how much
> of this is reproduced in ConTeXt): 1. Spelling conventions, 2. Hyphenation.
> For the latter, a classification by historical periods clearly makes no
> sense, but there is some trut
entions, 2. Hyphenation.
For the latter, a classification by historical periods clearly makes no
sense, but there is some truth to the fact that an orthography with no
u/v or i/j distinction is closer to the way Latin was written in
classical times (if only very slightly); while using both u and v,
>
> \defineframed[infobox][frame=off,width=max,background=infolayer,setups=infolayer:place]
>
> \define[2]\Info
> {\par
>\setvariable{infotext}{points}{#2}%
>\infobox[height=#1]{}}
>
> \starttext
>
> \startitemize[n]
> \starthead{Question 1}
>
riable{infotext}{points}}}
\stopsetups
\defineframed[infobox][frame=off,width=max,background=infolayer,setups=infolayer:place]
\define[2]\Info
{\par
\setvariable{infotext}{points}{#2}%
\infobox[height=#1]{}}
\starttext
\startitemize[n]
\starthead{Question 1}
\Info{9cm}{20 \p
]
\setupmarginframed[inmargin][align=middle,location=outer]
\def\Info#1{\margindata[inmargin]{\rotate{#1}\ignorespaces}}
\starttext
\startitemize[n]
\item Question 1
\vskip8cm
\Info{20 \periods[3] 15 \periods[3] 10}
\vskip1cm
\item Question 2
\vskip8cm
\Info{20 \periods[3] 15 \periods[3] 10}
\page
- the distinction was there because we could
fake gray using small periods so it was a different background plugin)
(just like nowadays \encoding[utf] is not needed and colors are enabled
by default)
Hans
Hi Hans and Wolfgang,
Thank you for your suggestions. It meets my expectations, but I'll try
to understand the codes later!
Fabrice
___
If your question is of interest to others as well, please add an entry to the
Am 06.03.2015 um 18:42 schrieb Fabrice Couvreur fabrice1.couvr...@gmail.com:
Hi,
Is it possible to change the shape of the dots of macro \periods[n] to be
like the dots of macro \definefiller[dots][left=\dontleavehmode,
right=\hskip\ZeroPoint\par] ?
You can change the width of each
Hi,
Is it possible to change the shape of the dots of macro \periods[n] to be like
the dots of macro \definefiller[dots][left=\dontleavehmode, right=\hskip\
ZeroPoint\par] ?
Best regards,
Fabrice
___
If your question
On 3/6/2015 6:42 PM, Fabrice Couvreur wrote:
Hi,
Is it possible to change the shape of the dots of macro \periods[n] to
be like the dots of macro \definefiller[dots][left=\dontleavehmode,
right=\hskip\ZeroPoint\par] ?
% in cont-new.mkiv :
\unprotect
\def\periodsymbol {.}
\unexpanded\def
Am 06.03.2015 um 20:02 schrieb Hans Hagen pra...@wxs.nl:
On 3/6/2015 6:42 PM, Fabrice Couvreur wrote:
Hi,
Is it possible to change the shape of the dots of macro \periods[n] to
be like the dots of macro \definefiller[dots][left=\dontleavehmode,
right=\hskip\ZeroPoint\par] ?
% in cont
On 3/6/2015 8:18 PM, Wolfgang Schuster wrote:
Am 06.03.2015 um 20:02 schrieb Hans Hagen pra...@wxs.nl:
On 3/6/2015 6:42 PM, Fabrice Couvreur wrote:
Hi,
Is it possible to change the shape of the dots of macro \periods[n] to
be like the dots of macro \definefiller[dots][left=\dontleavehmode
Hi Hans,
It works perfectly, thank you.
Fabrice
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
On 1/18/2015 10:01 PM, Fabrice wrote:
Hi Hans,
The size of the float does not center the frame unless I replace by
\dorecurse{5}{\filler[dots]} by \dorecurse{10}{\filler[dots]}.
Is there a better way ?
Thanks,
Fabrice
% macros=mkvi
Hi Hans,
The size of the float does not center the frame unless I replace by
\dorecurse{5}{\filler[dots]} by \dorecurse{10}{\filler[dots]}.
Is there a better way ?
Thanks,
Fabrice
% macros=mkvi
\definefiller[dots][left=\dontleavehmode,right=\hskip\zeropoint\par]
\definefloat
[recipe]
On the subject of recipes, Fabrice clearly should have come to the 8th
ConTeXt Meeting that took place on September 8-13, 2014 at Bassange,
Belgium...
;-)
Alan
On Mon, 5 Jan 2015 22:49:39 +0100
Hans Hagen pra...@wxs.nl wrote:
On 1/5/2015 6:58 PM, Fabrice wrote:
Hi,
How to make the dotted
I am impressed !
Best regards,
Fabriçe
Envoyé de mon iPad
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
Hi Alan,
What should I include ?
Fabrice
Envoyé de mon iPad
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
On 1/5/2015 6:58 PM, Fabrice wrote:
Hi,
How to make the dotted lines stop at the edge of the frame?
\definefiller[dots][left=\dontleavehmode,right=\hskip\zeropoint]
\definecolor[H1prime][c=0.50, m=0.00, y=1.00, k=0.00]
\definecolor[H4][c=0.07, m=0.00, y=0.15, k=0.00]
\starttext
Hi,
How to make the dotted lines stop at the edge of the frame?
\definefiller[dots][left=\dontleavehmode,right=\hskip\zeropoint]
\definecolor[H1prime][c=0.50, m=0.00, y=1.00, k=0.00]
\definecolor[H4][c=0.07, m=0.00, y=0.15, k=0.00]
\starttext
\startitemize[n][stopper={.},style=bold]
Hi,
Is it possible to redefine the command \periods[n] to have a line that goes
from the end of the word to the edge of the page without having to play on
the number n ?
Regards,
Fabrice
\starttext
\startitemize[a][stopper=),style=bold]
\item $x\mapsto -x^2+x+1$ : \periods[66]
\item $x\mapsto 2x
On Tue, May 20, 2014 at 10:30 AM, Fabrice Couvreur
fabrice1.couvr...@gmail.com wrote:
Hi,
Is it possible to redefine the command \periods[n] to have a line that
goes from the end of the word to the edge of the page without having to
play on the number n ?
Regards,
Fabrice
\starttext
Am 20.05.2014 um 10:47 schrieb luigi scarso luigi.sca...@gmail.com:
On Tue, May 20, 2014 at 10:30 AM, Fabrice Couvreur
fabrice1.couvr...@gmail.com wrote:
Hi,
Is it possible to redefine the command \periods[n] to have a line that goes
from the end of the word to the edge of the page
Hello,
@ Luigi @Wolfgang Thanks for your suggestions.
Since I want to continue my learning ConTeXt, I will use the command
\filler[dots].
Can we do the same thing if there is no text in the beginning ?
Fabrice
___
Am 20.05.2014 um 19:50 schrieb Fabrice couvreur.fabr...@wanadoo.fr:
Hello,
@ Luigi @Wolfgang Thanks for your suggestions.
Since I want to continue my learning ConTeXt, I will use the command
\filler[dots].
Can we do the same thing if there is no text in the beginning ?
You can add
Perfect !
thank you,
Fabrice
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage :
Le Fri, 28 Mar 2014 16:28:13 +0100,
Hans Hagen pra...@wxs.nl a écrit :
On 3/28/2014 3:45 PM, Stéphane Goujet wrote:
Hello again,
If you look at one of the images in my previous post (I attached
it here again), you may notice the ellipsis (that has 5 periods
instead of 3
Hello again,
If you look at one of the images in my previous post (I attached it
here again), you may notice the ellipsis (that has 5 periods instead of
3, but that is not my concern). Its last period is bigger, to indicate
the fusion of the ellipsis and the sentence final period. It does
On 3/28/2014 3:45 PM, Stéphane Goujet wrote:
Hello again,
If you look at one of the images in my previous post (I attached it
here again), you may notice the ellipsis (that has 5 periods instead of
3, but that is not my concern). Its last period is bigger, to indicate
the fusion
behaviour. Commas get a thin space,
periods get nothing.
* autopunctuation=yes — manual control for commas. Commas followed by
a space get a thin space; periods, and commas followed by something
else, do not.
* autopunctuation=all — like `yes`; and periods, too, get a thin space
unless suppressed
Example
strips path and extenstion, e.g.
file.nameonly('a/b/cod.doc') returns 'cod'.
You can see the file.* functions in l-file.lua.
string.totable splits a string, and returns the pieces as an array. In
this case, the string is split at the periods.
table.concat combines a table into a string, optionally
\scratchbox}%
\egroup}
which does export periods (but spaced, as expected).
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477
Am 20.08.2011 um 20:57 schrieb Marcin Borkowski:
Do I get it correctly that \unknown yields three characters (dots) in
the resulting pdf and … one (if it's available in the font, at least)?
Yes, \unknown are three periods which are separated by a small space
and … is one character. Sometimes
into a MPinclusions. I have to do LoadPageState in each
graphic though.
%\showframe
\setuppapersize[A5][A5]
\setuppagenumbering[alternative=doublesided]
\startMPinclusions
numeric periods, width;
path wave;
periods := 3 + 1/4;
width := periods * 2*pi;
wave:= origin for x=0 step 0.1 until
with a reuseMPgraphic. Also, I pulled out the definition of
the wave into a MPinclusions. I have to do LoadPageState in each
graphic though.
%\showframe
\setuppapersize[A5][A5]
\setuppagenumbering[alternative=doublesided]
\startMPinclusions
numeric periods, width;
path wave;
periods := 3 + 1/4
the bottomframe ends and move on to the page
border. Also, the graphic is placed in the page background layer, but
nevertheless the text after the the graphic is shifted down.
\startuniqueMPgraphic{wave}
numeric periods, width;
path wave;
periods := 3 + 1/4;
width := periods * 2*pi;
wave
On Fri, 1 Apr 2011, Tim Steenvoorden wrote:
(Untested).
\startuniqueMPgraphic{wave}
numeric periods, width;
path wave;
periods := 3 + 1/4;
width := periods * 2*pi;
wave:= origin for x=0 step 0.1 until width:
-- (x,x*sin(x))
endfor;
pickup pencircle scaled 1pt;
draw
\ and \ldots?
\ldots uses the math character (0x2026), while \unknown
fakes the dots. You can change the spacing between the dots using
\periods[1mm]
☺☹
Does not work at the moment. I'll examine it.
You need a font that has these characters (lm does not, that is why I used
libertine
Works. What is the difference between \unknown\ and \ldots?
\ldots uses the math character (0x2026), while \unknown fakes the dots. You
can change the spacing between the dots using \periods[1mm]
Okay, I'll play with it.
☺☹
Does not work at the moment. I'll examine it.
You need
correctly by all parts involved. If you want to know a bit
more about it, have a look at all the efforts Hans makes
to sanitize font names so they will be found in the mkiv
font database; taking out all the spaces and periods and
whatnot. And yet, next week, some smart font designer
second opinions?
Adding the \dots(m|i|b|) etc from amsmath is a good idea. I will look
into that.
+1. I normally use $x, \dots\, ,x$ because then the spacing between
the periods looks the same as between the commas and the periods, which
I prefer. I personally appreciate the wider spacing in \dots
.
When I run the KingsTest.tex in ConTeXt Minimals Mark II I get proper output (I
have two extra periods but that is probably my fault). When I run the same file
using Mark IV I get the title only in the output.
Thanks for looking into this.
Charlie
KingsTest.tex
Description: TeX document
LaTeX to
produce the preview and that looks perfect.
When I run the KingsTest.tex in ConTeXt Minimals Mark II I get proper output
(I have two extra periods but that is probably my fault). When I run the same
file using Mark IV I get the title only in the output.
Thanks for looking
On Friday 22 October 2010 11:38:35 Charles Doherty wrote:
When I run the KingsTest.tex in ConTeXt Minimals Mark II I get proper
output (I have two extra periods but that is probably my fault). When I
run the same file using Mark IV I get the title only in the output.
The problem appears
(the preview style is abbrev). BibDesk uses LaTeX to produce
the preview and that looks perfect.
When I run the KingsTest.tex in ConTeXt Minimals Mark II I get proper output (I
have two extra periods but that is probably my fault). When I run the same file
using Mark IV I get the title only
to produce
the preview and that looks perfect.
When I run the KingsTest.tex in ConTeXt Minimals Mark II I get proper output (I
have two extra periods but that is probably my fault). When I run the same file
using Mark IV I get the title only in the output.
fixed in next beta ... it probably never
On Oct 22, 2010, at 4:47 PM, Hans Hagen wrote:
fixed in next beta ... it probably never worked in mkiv so it went unnoticed
quite long
Excellent - works now! Charles should look into the output; those spurious
periods are not quite right, but I don't have time now to look into them
) where there are double periods.
Adding any more \DLs or \VLs results in not being able to translate the file or
other errors. Currently the horizontal lines are not where they should be (now
on Mo, Mi, Fr) but kind of evenly spread.
Lastly: How do I control row height?
thanks!
Martin
much spacing...
On the other hand, the spacing before \dots is just right, but the spacing after \dots is
too small: the spaces between commas and periods ,..., should all be the same.
Is this a bug? Can this be changed by a global option or something? Thanks for
any help in advance.
Does
}, a variable.}
\stoptext
Wolfgang
Thanks for responding Wolfgang. But this solution has some problems.
The first problem is that it only works for commas. I'm sure I can
figure out how to next the \doifnextcharelse commands to add periods,
question marks, and exclamation points
]{Section one}
It was in \in{section}[sec:one].
4) \digits command falls over at periods or commas with \textfont1 is
undefined (character 58).
\digits{1.6}
5) \infull command does not work for abbreviations: falls over with
Missing } inserted.
\abbreviation {KF} {Kalman filter}
Rudolph Kalman
]{Section one}
It was in \in{section}[sec:one].
4) \digits command falls over at periods or commas with \textfont1 is
undefined (character 58).
\digits{1.6}
5) \infull command does not work for abbreviations: falls over with
Missing } inserted.
\abbreviation {KF} {Kalman filter}
Rudolph Kalman
. reference to section 1 appears
as '11' or ref to section 1.1 appears as '1.11.1')
\section[sec:one]{Section one}
It was in \in{section}[sec:one].
4) \digits command falls over at periods or commas with \textfont1 is
undefined (character 58).
\digits{1.6}
5) \infull command does not work
]
\stoptypescript
\usetypescript[Test]
\setupbodyfont[Test,12pt]
\starttext
fine's flops: 1 -- 2 --- 3
\stoptext
priority: medium for me (since it can be worked around, but still
needs fixing)
%%
4. Spaces, esp. after periods
\font\one=cmr10
\font
Wolfgang,
| \unexpanded\def\fourdots{{\def\periodswidth{.3em}\periods[4]}}
|
| \starttext
| Hello\fourdots\ World\fourdots
|
| Hello\fourdots\ World.
| \stoptext
Thanks for the macro! It's almost perfect. . . . I thought I was
imagining things, but the distance between the last letter
\def\fourdots
{\ldotp\ldotp\ldotp\ldotp}
Wolfgang
Am 11.05.2009 um 23:14 schrieb Ryo Furue:
Wolfgang,
| \unexpanded\def\fourdots{{\def\periodswidth{.3em}\periods[4]}}
|
| \starttext
| Hello\fourdots\ World\fourdots
|
| Hello\fourdots\ World.
| \stoptext
Thanks for the macro! It's almost
Am 08.05.2009 um 22:22 schrieb Ryo Furue:
\starttext
Hello\ldots. World.\ldots
Hello\unknown. World.\unknown
Hello\unknown World.
\stoptext
\unexpanded\def\fourdots{{\def\periodswidth{.3em}\periods[4]}}
\starttext
Hello\fourdots\ World\fourdots
Hello\fourdots\ World.
\stoptext
Hello ConTeXt folks,
I'm quite new to ConTeXt. I like it.
It's way more systematic than LaTeX.
Here's my first question. When omitting the last
part of a sentence, I want four periods:
This is a long sentence which\ldots.
LaTeX produces equally-spaced four periods,
but with ConTeXt
Ryo Furue wrote:
Hello ConTeXt folks,
I'm quite new to ConTeXt. I like it.
It's way more systematic than LaTeX.
Here's my first question. When omitting the last
part of a sentence, I want four periods:
This is a long sentence which\ldots.
which\unknown
Hello Hans,
| Hello ConTeXt folks,
| I'm quite new to ConTeXt. I like it.
| It's way more systematic than LaTeX.
| Here's my first question. When omitting the last
| part of a sentence, I want four periods:
|This is a long sentence which\ldots.
|
| which\unknown
Thanks
On Sat, Mar 14, 2009 at 08:52, Aditya Mahajan wrote:
Also, we put periods after section numbers, so no 1.2
Section, but rather 1.2. Section.
\setuplabeltext [pl] [section={{},{.}}]
Hello Aditya,
Interesting trick, thanks. But the problem is that references then
ignore the dot. So \in[ref
Am 17.03.2009 um 20:12 schrieb Mojca Miklavec:
On Sat, Mar 14, 2009 at 08:52, Aditya Mahajan wrote:
Also, we put periods after section numbers, so no 1.2
Section, but rather 1.2. Section.
\setuplabeltext [pl] [section={{},{.}}]
Hello Aditya,
Interesting trick, thanks. But the problem
On Tue, Mar 17, 2009 at 20:56, Wolfgang Schuster wrote:
Am 17.03.2009 um 20:12 schrieb Mojca Miklavec:
On Sat, Mar 14, 2009 at 08:52, Aditya Mahajan wrote:
Also, we put periods after section numbers, so no 1.2
Section, but rather 1.2. Section.
\setuplabeltext [pl] [section
Mojca Miklavec wrote:
On Tue, Mar 17, 2009 at 20:56, Wolfgang Schuster wrote:
Am 17.03.2009 um 20:12 schrieb Mojca Miklavec:
On Sat, Mar 14, 2009 at 08:52, Aditya Mahajan wrote:
Also, we put periods after section numbers, so no 1.2
Section, but rather 1.2. Section.
\setuplabeltext [pl
it :) :) :) But maybe
that's not the right solution, I just didn't care too much.
Also, we put periods after section numbers, so no 1.2
Section, but rather 1.2. Section. What is the ConTeXt way to have
such things for different languages?
We do that too. The code below is a dirty hack that achives
to language will make it extremely
difficult.
A related problem is dashes; where the
English use an em-dash without any spaces, the Polish use an en-dash
with spaces of around 0.2em (the left one unbreakable, i.e., with
\penalty1).
Don't know.
Also, we put periods after section numbers, so
comprehensive list, of course)
enabled by \mainlanguage[pl]? A related problem is dashes; where the
English use an em-dash without any spaces, the Polish use an en-dash
with spaces of around 0.2em (the left one unbreakable, i.e., with
\penalty1). Also, we put periods after section numbers, so
In a message some time ago, Wolfgang suggested that
\def\ {\thinspace}
would serve to get non-expanding or non-stretchable spaces after
periods that occur within sentences and in bibliographies. When I
discovered that, while this worked well in limited contexts, in a
lengthy bibliography
{ }{.}{.}
Why: prevents double periods after the title. It's what you did for
several other publication types in the version you sent me on August 10.
2. line 384: commented out insertpublisher line
Why: this is the entry for unpublished documents so I wasn't sure why
it was there. More
1 - 100 of 135 matches
Mail list logo
